Don't expire cookie with later setting in the same headers #1584
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm interacting with a server that likes to simultaneously expire a cookie and give it a new value in the same headers:
This isn't spec, as I understand it, but it turns out the browsers don't care. They just use the last value given.
So this PR updates httpie to behave in the same way, by ignoring an earlier expiration in favor of a later setting in the same headers.
Without this change, httpie drops the cookie rather than setting it, which makes interacting with this particular server quite difficult.